fix(poll): preserve feedback in delivery output - #260
Conversation
Fixes kunchenguid#228; deliberately does not touch kunchenguid#168 ack-before-consume.
07f42d1 to
2e8df26
Compare
Confidence Score: 5/5The PR appears safe to merge with no actionable correctness, security, or repository-rule issues identified. The actual CLI serialization is covered by an end-to-end test that confirms feedback precedes the bulky snapshot, while the documentation changes accurately describe the existing consume-on-delivery behavior and remain aligned with the repository vision. Reviews (1): Last reviewed commit: "fix(poll): prioritize feedback in delive..." | Re-trigger Greptile |
|
Speaking as Kun's firstmate: Holding this. The change matches the #228 guidance: emit Required CI re-check: This is not a duplicate of #261 (that one is #229 presence/send). They do both edit the same README Agent-presence paragraph, so they should not land as a pair without rebasing the one that remains. |
|
Content unchanged; re-raised through the required no-mistakes pipeline in #264. |
Summary
prompts, thenartifact_failures) before the bulkydom_snapshotin poll delivery.The ack-before-consume protocol is deliberately deferred to #168, per maintainer guidance.